feat(blog): add How Prisma Builds with Agentic AI post#7684
feat(blog): add How Prisma Builds with Agentic AI post#7684ArthurGamby merged 5 commits intomainfrom
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughAdded a new MDX blog post at apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx documenting Prisma’s agentic engineering practices: spec-first workflows, adversarial spec reviews, a trust-ladder for delegation, local agent verification (tests/linters/types), human gatekeeping, and embedded media. (34 words) Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
There was a problem hiding this comment.
🧹 Nitpick comments (1)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx (1)
2-3: Align title and slug phrasing for URL consistencyLine 2 uses “Builds” while Line 3 uses “build”. Consider updating the slug to
how-prisma-builds-with-agentic-aiso permalink grammar matches the published title and avoids awkward URL phrasing.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx` around lines 2 - 3, The title and slug are inconsistent: the frontmatter key "title" is "Agentic Engineering: How Prisma Builds with AI" while the "slug" uses "how-prisma-build-with-agentic-ai"; update the slug value to "how-prisma-builds-with-agentic-ai" so the slug grammar matches the title ("Builds") and the permalink reads naturally, ensuring you modify the "slug" line in the file to the new value.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx`:
- Around line 2-3: The title and slug are inconsistent: the frontmatter key
"title" is "Agentic Engineering: How Prisma Builds with AI" while the "slug"
uses "how-prisma-build-with-agentic-ai"; update the slug value to
"how-prisma-builds-with-agentic-ai" so the slug grammar matches the title
("Builds") and the permalink reads naturally, ensuring you modify the "slug"
line in the file to the new value.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 3fa91cba-1f9d-4c60-81a5-3c4573ea5fe7
⛔ Files ignored due to path filters (4)
apps/blog/public/authors/arthur-gamby.pngis excluded by!**/*.pngapps/blog/public/how-prisma-build-with-agentic-ai/imgs/local-feedback-loop.pngis excluded by!**/*.pngapps/blog/public/how-prisma-build-with-agentic-ai/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/how-prisma-build-with-agentic-ai/imgs/the-trust-ladder.pngis excluded by!**/*.png
📒 Files selected for processing (1)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx
Replace raw markdown blockquotes with the blog's <Quotes> component for consistent styling with speaker name and position attribution. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx`:
- Around line 2-3: The slug in the frontmatter uses
"how-prisma-build-with-agentic-ai" which conflicts with the title "Agentic
Engineering: How Prisma Builds with AI"; update the slug to
"how-prisma-builds-with-agentic-ai" and also rename or update any related
asset/path names and internal links referenced elsewhere in this file (the
entries around the other frontmatter/asset lines) so they consistently use
"builds" to match the title and avoid URL/SEO mismatches.
- Line 112: Replace the non-hyphenated compound "error handling strategy" with
the hyphenated compound "error-handling strategy" in the sentence that currently
reads "Agents don't know what they don't know about your system...or the error
handling strategy that accounts for a third-party service's quirky failure
modes." Update that exact phrase to "error-handling strategy" to use the correct
compound modifier.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: d18af161-15ee-4c5b-a1c1-c8634372fcac
📒 Files selected for processing (1)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx
Set the how-prisma-build-with-agentic-ai article date to today's publication date. Made-with: Cursor
There was a problem hiding this comment.
♻️ Duplicate comments (2)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx (2)
112-112:⚠️ Potential issue | 🟡 MinorUse a hyphenated compound modifier for clarity.
At Line 112,
error handling strategyshould beerror-handling strategy.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx` at line 112, Change the phrase "error handling strategy" to the hyphenated compound modifier "error-handling strategy" wherever that exact phrase appears (specifically replace the occurrence "error handling strategy" in the sentence containing "third-party service's quirky failure modes"); update the text node/content that contains that string so the compound adjective is hyphenated for clarity.
2-3:⚠️ Potential issue | 🟡 MinorAlign slug and asset path wording with the published title.
Line 3 still uses
how-prisma-build-with-agentic-aiwhile the title at Line 2 says “Builds.” Please standardize slug/path naming (builds) to avoid avoidable URL and metadata inconsistency.Also applies to: 9-10
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx` around lines 2 - 3, The frontmatter slug value ("how-prisma-build-with-agentic-ai") does not match the title wording ("Agentic Engineering: How Prisma Builds with AI"); update the slug and any other asset/path occurrences that use "how-prisma-build-with-agentic-ai" (including the second occurrence referenced) to use "how-prisma-builds-with-agentic-ai" so the slug/path matches the published title; ensure you update both frontmatter keys (slug) and any asset path variables that reference the old slug.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx`:
- Line 112: Change the phrase "error handling strategy" to the hyphenated
compound modifier "error-handling strategy" wherever that exact phrase appears
(specifically replace the occurrence "error handling strategy" in the sentence
containing "third-party service's quirky failure modes"); update the text
node/content that contains that string so the compound adjective is hyphenated
for clarity.
- Around line 2-3: The frontmatter slug value
("how-prisma-build-with-agentic-ai") does not match the title wording ("Agentic
Engineering: How Prisma Builds with AI"); update the slug and any other
asset/path occurrences that use "how-prisma-build-with-agentic-ai" (including
the second occurrence referenced) to use "how-prisma-builds-with-agentic-ai" so
the slug/path matches the published title; ensure you update both frontmatter
keys (slug) and any asset path variables that reference the old slug.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: c32b6f07-d025-47d9-af3c-3f29adc1cf34
📒 Files selected for processing (1)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx
Summary
Voice audit (
devrel-voice)Passes:
Minor flags (cosmetic, not blocking):
Recommendation: No voice pass needed. The post is already well within Prisma voice guidelines. It leads with usefulness, sounds like a person, is honest about tradeoffs, and has a pulse. Running
devrel-voiceon it would risk over-polishing writing that already works.Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit